Skip to content

Enhance auth feature #63

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Jul 28, 2025
Merged

Enhance auth feature #63

merged 7 commits into from
Jul 28, 2025

Conversation

fulleni
Copy link
Member

@fulleni fulleni commented Jul 28, 2025

Description

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

fulleni added 7 commits July 28, 2025 19:19
- Add pinput package to pubspec.yaml for improved text input handling
- Update pubspec.lock with new dependencies:
  - pinput: ^5.0.1
  - universal_platform: ^1.1.0 (transitive dependency)
- Add Arabic and English translations for the resend verification code button text during cooldown period
- Include placeholders for seconds countdown in both languages
- Add cooldownEndTime field to track the end time of cooldown for requesting a new code
- Update copyWith method to include cooldownEndTime parameter and clearCooldownEndTime option
- Modify props list to include cooldownEndTime
- Add new event to handle sign-in code request cooldown completion
- Update authentication bloc to include cooldown reset functionality
- Add cooldown functionality to prevent frequent sign-in code requests
- Introduce new event AuthenticationCooldownCompleted
- Update AuthenticationState to include cooldownEndTime
- Implement logic to check cooldown status before processing new code requests
- Set cooldown duration to 60 seconds after successful code request
- Add cooldown functionality to prevent frequent sign-in code requests
- Implement Timer to handle countdown and update UI accordingly
- Update AuthenticationBloc to manage cooldown end time
- Modify UI to show cooldown remaining time and disable button when necessary
…ication

- Remove TextFormField and related padding
- Add Pinput widget for 6-digit OTP verification
- Implement default and focused pin themes
- Add length validation and error handling
- Improve accessibility with onCompleted event
@fulleni fulleni merged commit 2f6fdc4 into main Jul 28, 2025
0 of 2 checks passed
@fulleni fulleni deleted the enhance_auth_feature branch July 28, 2025 18:37
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @fulleni, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the authentication feature by introducing a robust cooldown mechanism for sign-in code requests, improving security and preventing abuse. Concurrently, it refines the user interface for entering verification codes, providing a smoother and more informative experience for users.

Highlights

  • Authentication Cooldown: Implemented a 60-second cooldown mechanism for requesting sign-in codes to prevent excessive requests. This includes state management in the AuthenticationBloc and a client-side timer in the UI.
  • Enhanced Code Entry UI: Replaced the standard TextFormField with the pinput package for a more intuitive and visually appealing verification code input experience on the EmailCodeVerificationPage.
  • Dynamic UI Feedback: The 'Send Code' button on the RequestCodePage now dynamically displays a countdown during the cooldown period, informing the user when they can request a new code.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The code changes introduce a cooldown feature for sign-in code requests and use the pinput package for verification, improving UI/UX. There are a couple of issues related to timer management and event handling that should be addressed to improve the robustness of the implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant